Remote decoupled application persistent state apparatuses, methods and systems

ABSTRACT

A method including receiving a selection from a first user device associated with a user, creating and storing a first cookie associated with states of a user account of the user that reflects the selection, and receiving, from a second user device, a request for state data related to the states of the user account. The method includes identifying the first cookie in response to the request for state data and determining a platform type of the second user device. The method includes generating a second cookie compliant with the platform type of the second user device based on the first cookie. The method includes sending the generated second cookie to the second user device, the second cookie including instructions to present the selection on the second user device via the platform type of the second user device.

This application is a continuation of U.S. patent application Ser. No. 16/283,251, filed Feb. 22, 2019, which is a continuation of U.S. patent application Ser. No. 14/216,351, filed Mar. 17, 2014, now U.S. Pat. No. 10,242,358, which claims priority to U.S. Patent Application Ser. No. 61/798,483, filed Mar. 15, 2013, and is a continuation of U.S. patent application Ser. No. 13/624,779, filed Sep. 21, 2012, which is a continuation-in-part of U.S. patent application Ser. No. 13/589,053, filed Aug. 17, 2012, which claims priority to: U.S. provisional patent application Ser. No. 61/525,168, filed Aug. 18, 2011; U.S. provisional patent application Ser. No. 61/537,421, filed Sep. 21, 2011; and U.S. provisional patent application Ser. No. 61/668,441 filed Jul. 5, 2012. The entire contents of the aforementioned applications are expressly incorporated by reference herein.

This application for letters patent disclosure document describes inventive aspects directed at various novel innovations (hereinafter “disclosure”) and contains material that is subject to copyright, mask work, and/or other intellectual property protection. The respective owners of such intellectual property have no objection to the facsimile reproduction of the disclosure by anyone as it appears in published Patent Office file/records, but otherwise reserve all rights.

FIELD

The present innovations are directed generally to digital wallets and account management, and more particularly, to REMOTE DECOUPLED APPLICATION PERSISTENT STATE APPARATUSES, METHODS AND SYSTEMS.

BACKGROUND

Consumers using the World Wide Web browse product listings of merchants and make purchases on selected products. Electronic data can be stored in computers and other storage devices for future access.

SUMMARY

In accordance with the teachings provided herein, systems, methods, non-transitory computer-readable medium, and apparatuses are disclosed for operation upon data processing devices for processing digital wallet transaction-related persistent states, such as by: receiving, by use of one or more processors, a wallet transaction-related persistent state update request identifying a wallet user, wherein the wallet transaction-related persistent state update request includes wallet persistent state payload; storing, by use of the one or more processors, the wallet persistent state payload associated with the wallet user; receiving, by use of the one or more processors, a wallet persistent state search criteria from the wallet user; providing, by use of the one or more processors, the wallet persistent state search results to the wallet user; receiving, by use of the one or more processors, a wallet persistent state selection; and generating, by use of the one or more processors, the wallet persistent state presentation based on the wallet persistent state selection.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying appendices and/or drawings illustrate various non-limiting, example, innovative aspects in accordance with the present descriptions:

FIG. 1 shows a block diagram illustrating example cookie/states storage in some embodiments of the P-STATE;

FIG. 2 shows a block diagram illustrating example cookie/states storage data flow in some embodiments of the P-STATE;

FIG. 3 shows a logic flow diagram illustrating example cookie/states storage component in some embodiments of the P-STATE;

FIGS. 4A-4C show user interfaces illustrating example cookie/states storage in some embodiments of the P-STATE;

FIG. 5 shows a block diagram illustrating example cookie states search presentation data flow in some embodiments of the P-STATE;

FIG. 6 shows a logic flow diagram illustrating example cookie states search presentation component in some embodiments of the P-STATE;

FIG. 7 shows a block diagram illustrating example cookie states reload/recreate data flow in some embodiments of the P-STATE;

FIG. 8 shows a logic flow diagram illustrating example cookie states reload/recreate component in some embodiments of the P-STATE;

FIG. 9 shows a block diagram illustrating embodiments of a P-STATE controller.

The leading number of each reference number within the drawings indicates the figure in which that reference number is introduced and/or detailed. As such, a detailed discussion of reference number 101 would be found and/or introduced in FIG. 1 . Reference number 201 is introduced in FIG. 2 , etc.

DETAILED DESCRIPTION

Various embodiments of the P-STATE facilitate an enriched user experience for digital wallet consumers and allow the consumers to store the cookies and the states of their browsing and purchasing history with their digital wallet. In some embodiments, the digital wallet server serves as a cloud based storage to the merchant so that the wallet consumers may retrieve any states they had in the past with this merchant. In some embodiments, the cookie that the wallet stores may have multiple states and the consumer may choose go to any random state and view the page. In some embodiments, because the cookies and states are stored with the digital wallet server, it may be shared across platform. For example, a consumer is at the kiosk at a merchant physical store and desires to purchase the items he looked for last night on this merchant's website. The P-STATE may identify the consumer's digital wallet and bring the items up at the kiosk. For another example, a consumer is at a airplane and desires to watch the movie he purchased before at home. The P-STATE may retrieve his prior purchase cookies and recognize that he has already paid for that (although with another device) and provide the movie to him.

P-STATE

FIG. 1 shows a block diagram illustrating example cookie/states storage in some embodiments of the P-STATE. One possible cookie state 101 may include a timestamp of when the state takes place 103, the merchant 105, the shopping cart status 107, the shipper 109, the offer 111, the payment method 113, the checkout status 115, the search criteria (e.g., T-shirt) 117, the search results list 119, the purchase status 121, the platform the consumer is using (e.g., iphone, Android, merchant kiosk, point of sale, etc.) 123. The timestamp may be in the format of 2005-02-03. The merchant of the order may be e-commerce sites such as Amazon. The search criteria may be the name of the product of interest, such as T-shirt. Another possible cookie state 125 may be the webpage providing the search results related to the search criteria (e.g., T-shirt) to the consumer. In some embodiments, it may also have the timestamp, merchant, shopping cart, shipper, offer, payment method, checkout status, purchase status, and order platform. Meanwhile, it may have an empty search criteria field 129, and some products in the search results list, such as blue T-shirt, pink T-shirt, and so forth. The reason may be that the search criteria may have been processed by the system and search results may have been generated. The consumer may choose to add one of the products 9 e.g., blue T-shirt) from the search results into the cart. In another possible cookie state 133, the timestamp, merchant, shopping cart, shipper, offer, payment method, search criteria, search results list, purchase status, and order platform may be the same as the previous cookie state. Meanwhile, its checkout status may include one or more items, the home address, payment method, and a link to the payment processing component. All possible cookie and states may be stored 137 to the cookies database 139. For example, the P-STATE server may issue PHP/SQL commands similar to the example listing below to store the cookies data 137 in a database:

-   -   <?PHP     -   header(‘Content-Type: text/plain’);     -   mysql_connect(“254.92.185.103”,$DBserver,$password); // access         database server     -   mysql_select(“CookieStates.SQL”); // select database to append     -   mysql_query(“INSERT INTO CookieStatesTable (state_session_ID         cookie_session_ID timestamp merchant shopping cart shipper offer         payment method checkout search search results purchase platform)     -   VALUES ($state_session_ID $cookie_session_ID timestamp(         )$merchant $shopping_cart $shipper $offer $payment_method         $checkout $search $search_results $purchase $platform”); // add         data to table in database     -   mysql_close(“CookieStates.SQL”); // close connection to database     -   ?>

In some embodiments, a cookie may have multiple states. In some embodiments, after the consumer places an order or finishes browsing with this merchant, multiple states may be combined to one cookie.

FIG. 2 shows a block diagram illustrating example cookie/states storage data flow in some embodiments of the P-STATE. A user 201 may submit the purchase action input 211 to the client device 202. The purchase action input may include search, add to cart, pay and so forth. After receiving the purchase action input, the client device may perform the requested purchase action and generate cookies 215. Then the client device may store the cookie states 220 to the client cookie database 207. An example of the cookie state structure is discussed in message 230. Examples of PHP/SQL commands to store 220 may be similar to example 137. Following that the client device may update the wallet determination 225 and determine how often the P-STATE server (e.g, wallet server) may need to be updated with the cookies. If the P-STATE server needs updating, then the client device may send the cookie states update package 230 to the P-State server 205. An example cookies/states update package substantially in the form of a HTTP(S) POST message 230 including XML-formatted data, is provided below:

-   -   POST/updateacookiestates.php HTTP/1.1     -   Host: www.P-STATE.com     -   Content-Type: Application/XML     -   Content-Length: 667     -   <?XML version=“1.0” encoding=“UTF-8”?>     -   <cookie_states_update_package>         -   <update_timestamp>2010-05-06 05:00</update_timestamp>         -   <last_update_timestamp>2010-05-05             05:00</last_update_timestamp>         -   <wallet_id>joesmith@gmail.com</wallet_id>         -   <cookie_session_ID>123adg             -   <statesessionID>1             -   <timestamp>2010-05-05-09:12</timestamp>             -   <merchant_id>A12345</merchant_id>             -   <merchant>Amazon</merchant>             -   <merchant_session_id>vme0345</merchant_session_id>         -   <merchant_connection_server>159.2.8.45</merchant_connection_server>             -   <shopping_cart></shopping_cart>             -   <shipper></shipper>             -   <offer></offer>             -   <payment_method></payment_method>             -   <checkout></checkout>             -   <search>T-shirt</search>             -   <search_results></search_results>             -   <purchase></purchase>             -   <platform></platform>         -   </state_session_ID>         -   <state_session_ID>2             -   <timestamp>2010-05-05-09:30</timestamp>             -   <merchant_id>A12345</merchant_id>             -   <merchant>Amazon</merchant>             -   <merchant_session_id>vme0345</merchant_session_id>         -   <merchant_connection_server>159.2.8.45</merchant_connection_server>             -   <shopping_cart></shopping_cart>             -   <shipper></shipper>             -   <offer></offer>             -   <payment_method></payment_method>             -   <checkout></checkout>             -   <search>T-shirt</search>             -   <search_results>1 Blue T-shirt, 2. Pink                 T-shirt</search_results>             -   <purchase></purchase>             -   <platform></platform>         -   </state_session_ID>         -   <state_session_ID>3             -   <timestamp>2010-05-05-09:40</timestamp>             -   <merchant_id>A12345</merchant_id>             -   <merchant>Amazon</merchant>             -   <merchant_session_id>vme0345</merchant_session_id>         -   <merchant_connection_server>159.2.8.45</merchant_connection_server>             -   <shopping_cart></shopping_cart>             -   <shipper></shipper>             -   <offer></offer>             -   <payment_method> Visa 1234</payment_method>             -   <checkout>1. Blue T-shirt, 2. Camera Total $320 Address:                 peace st. New York N.Y.</checkout>             -   <search>T-shirt</search>             -   <search_results></search_results>             -   <purchase></purchase>             -   <platform></platform>         -   </state_session_ID>         -   </cookie_session_ID>         -   <cookie_session_ID>523adg         -   <statesessionID>1             -   <timestamp>2011-05-05-09:12</timestamp>             -   <merchant_id>B12345</merchant_id>             -   <merchant>Bestbuy</merchant>             -   <merchant_session_id>vme1345</merchant_session_id>         -   <merchant_connection_server>259.2.8.45</merchant_connection_server>             -   <shopping_cart>Computer XXXX</shopping_cart>             -   <shipper>UPS</shipper>             -   <offer></offer>             -   <payment_method></payment_method>             -   <checkout></checkout>             -   <search></search>             -   <search_results></search_results>             -   <purchase></purchase>             -   <platform>iphone</platform>         -   </state_session_ID>         -   <state_session_ID>2             -   <timestamp>2011-05-05-10:30</timestamp>             -   <merchant_id>B12345</merchant_id>             -   <merchant>Bestbuy</merchant>             -   <merchant_session_id>vme1345</merchant_session_id>             -   <merchant_connection_server>259.2.8.45</merchant_connection_server>             -   <shopping_cart>Computer XXXX</shopping_cart>             -   <shipper>UPS</shipper>             -   <offer>20% off</offer>             -   <payment_method></payment_method>             -   <checkout></checkout>             -   <search></search>             -   <search_results></search_results>             -   <purchase></purchase>             -   <platform> iphone </platform>         -   </state_session_ID>         -   </cookie_session_ID>     -   </cookie_states_update_package>

After receiving the cookie states update package the P-State server may update the cookie states 234. Then the P-State server may store the cookie states 240 into the P-State cookies database 209. Examples of PHP/SQL commands to store 240 may be similar to example 137.

FIG. 3 shows a logic flow diagram illustrating example cookie/states storage component in some embodiments of the P-STATE. In some embodiments, the client may receive purchase action input, such as search, add to cart, and so forth 311. Then the client may determine whether the input includes a new merchant 313. If it does not include a new merchant, then the client may determine whether the transaction is complete 315. In some embodiments, it may determine whether a previous transaction is complete. If the transaction is not complete, then the client may determine if it is the first transaction 317. If the input includes a new merchant, or the transaction is complete, or it is the first transaction, then the client may set a new cookie flag 319. After that the client may create a new cookie 321. The client may also set the cookie flag to complete and store the cookie on the device 329. Then the client may create a new cookie state 325. After that and also if it does not involve a first transaction with the merchant 317, for each action that is queued 327, the client may create a new cookie state 325 and perform the received purchase action 323. Following that the client may store the cookie states to the client cookies database with performed action state information 331. Then the client may determine whether there is a wallet update quantum 333. If there is a wallet update quantum, then the client may update the wallet determination, such as to update every 5 minutes, or one hour, or 3 days, and so forth 335. After that the client may send cookie sates update package to the P-State server 337. Then the P-State server may update the cookie states 341. After that the P-State server may store the updated cookie states to the P-State cookies database 343. If ted is not a wallet update quantum, then the client may determine whether there is a next queued action 339. If there is a next queued action, then the client may receive purchase additional action input.

FIGS. 4A-4C show user interfaces illustrating example cookie/states storage in some embodiments of the P-STATE. Referring to FIG. 4A, in some embodiments, cookies and states (cookies and states may be referred to cookie states, cookies, or states in some instances) may be viewed in a timeline fashion. 405, 407, 409 are different cookie states and when the mouse lies on one state, a preview of this state may be seen 405. Cookies on the right 401 have a newer timestamp than the cookies on the left 403. Also a list of the cookies with file information may be shown underneath 411. In the preview window 405, you may choose different information to show. If you choose to view cart 413, you may see the merchant name, session id, timestamp, and a list of products in the cart. You may also search 415 in the cookies, view file info 423, preview the cookie 421, reload the cookie 419, and recreate the cookie 417. In some embodiments, reloading the cookie means the merchant still has the cookie loaded. The merchant may send the payload information and consumer's client device may load the cookie and generate for webpage or app's display. In some embodiments, recreating the cookie means the merchant may not have the cookie loaded. Based on the payload info in the stored cookie, the merchant may recreate the cookie and send to the consumer. The reloading and recreating features are discussed in more details in FIGS. 7 and 8 .

Referring to FIG. 4B, in some embodiments, cookies and states are searchable. You may put in a search term 431, for example boot, the P_STATE may return you the cookies and states with “boot” in it 437.

Referring to FIG. 4C, in some embodiments, consumer may also view the cookies in a list view 451. Timestamp 455, product 457, price 459, merchant 461, platform 463, coupons 465, shippers 467, payment method, and other information may be shown. For some products, consumers may view it in different platforms (for example, iPad 477, and merchant kiosk 479). In some embodiments, the cookies and states are searchable 453. Users may choose different categories to search.

FIG. 5 shows a block diagram illustrating example cookie states search presentation data flow in some embodiments of the P-STATE. In some embodiments, a user 501 may submit the cookie states search criteria input 511 to the client device 502. After receiving the search criteria input, the client device may look up cookie state or states associated with the search criteria 515. After that it may generate a cookie states presentation 520. Alternatively the client device may submit a cookie states search request with search criteria 530 to the P-State server 505. An example cookie states search request substantially in the form of a HTTP(S) POST message 530 including XML-formatted data, is provided below:

-   -   POST/cookiestatessearch.php HTTP/1.1     -   Host: www.P-STATE.com     -   Content-Type: Application/XML     -   Content-Length: 667     -   <?XML version=“1.0” encoding=“UTF-8”?>     -   <cookie_states_search_request>         -   <wallet_id>joesmith@gmail.com</wallet_id>         -   <wallet_digital_certificate>****</wallet_digital_certificate>         -   <search_target>cookies</search_target>         -   <search_criteria>boots</search_criteria>         -   <search_period_from>2005-01-03</search_period_from>         -   <search_period_to>2006-01-03</search_period_to>     -   </cookie_states_search_request>

Then the P-State server may look up the cookie state or states associated with the search criteria 535. After that the P-State server may send the cookie states search results 540 back to the client device. An example cookie states search results substantially in the form of a HTTP(S) PUSH message 540 including XML-formatted data, is provided below:

-   -   PUSH/cookiestatessearchresults.php HTTP/1.1     -   Host: www.P-STATE.com     -   Content-Type: Application/XML     -   Content-Length: 667     -   <?XML version=“1.0” encoding=“UTF-8”?>     -   <cookie_states_search_results>         -   <wallet_id>joesmith@gmail.com</wallet_id>         -   <cookie_session_ID>123adg             -   <state_session_ID>3                 -   <timestamp>2010-05-05-09:40</timestamp>                 -   <merchant_id>A12345</merchant_id>                 -   <merchant>Amazon</merchant>                 -   <merchant_session_id>vme0345</merchant_session_id>         -   <merchant_connection_server>159.2.8.45</merchant_connection_server>             -   <shopping_cart></shopping_cart>             -   <shipper></shipper>             -   <offer></offer>             -   <payment_method> Visa 1234</payment_method>             -   <checkout>1. baby boots 2. books Total $320 Address: 123                 peace st. New York N.Y.</checkout>             -   <search></search>             -   <search_results></search_results>             -   <purchase></purchase>             -   <platform></platform>         -   </state_session_ID>         -   </cookie_session_ID>             -   <cookie_session_ID>523adg                 -   <state_session_ID>1                 -   <timestamp>2011-05-05-09:40</timestamp>                 -   <merchant_id>M12345</merchant_id>                 -   <merchant>Macy's</merchant>                 -   <merchant_session_id>vme3345</merchant_session_id>         -   <merchant_connection_server>159.2.8.45</merchant_connection_server>             -   <shopping_cart></shopping_cart>             -   <shipper></shipper>             -   <offer></offer>             -   <payment_method> Visa 1234</payment_method>             -   <checkout>1. leather boots 2. computer Total $920                 Address: 123 peace st. New York N.Y.</checkout>             -   <search></search>             -   <search_results></search_results>             -   <purchase></purchase>             -   <platform></platform>             -   </state_session_ID>         -   </cookie_session_ID>     -   </cookie_states_search_results>

The client device then may generate the cookie states presentation. Then the client device may display the results 525 to the user.

FIG. 6 shows a logic flow diagram illustrating example cookie states search presentation component in some embodiments of the P-STATE. The client may receive cookie states search criteria input 6 oi. After that the client may look up cookie states associated with the search criteria 605. Then the client may determine whether the cookies are found 607. If the cookies are found, the client may load the cookie stats 609. If the cookies are not found, the client may send the cookie states search request with the search criteria to the P-State server 615. Following that the P-State server may look up the cookie state or states associated with the search criteria 620. Then the P-State server may send the cookie states search results to the client 625. After the client loads the cookie states or the P-State server sends the cookie states search results to the client, the client may generate cookie states presentation 630.

FIG. 7 shows a block diagram illustrating example cookie states reload/recreate data flow in some embodiments of the P-STATE. In some embodiments, the user may submit the cookie state(s) selection input 711 to the client device 702. Then the client device may determine the platform that is used, such as webpage, mobile app, and so forth, and load the cookies 715. After that the client device may reload or recreate the cookie state request message, such as payload cookie and states 720. An example reload/recreate cookie state request substantially in the form of a HTTP(S) POST message 720 including XML-formatted data, is provided below:

-   -   POST/reloadrecreatecookiestaterequest.php HTTP/1.1     -   Host: www.P-STATE.com     -   Content-Type: Application/XML     -   Content-Length: 667     -   <?XML version=“1.0” encoding=“UTF-8”?>     -   <reload_recreate_cookie_state_request>         -   <merchant_id>A12345</merchant_id>         -   <search_target>cookies</search_target>         -   <search_criteria>             -   <cookie_session_ID>123adg</cookie_session_ID>1             -   <statesessionID>3</state_session_ID>         -   </search_criteria>         -   <search_period_from>2005-01-03</search_period from>         -   <search_period_to>2006-01-03</search_period_to>     -   </reload_recreate_cookie_state_request>

Then the merchant server 705 may determine if the selected cookie state is still loaded 725. Then the merchant server may load the selected cookie state 730 and send the reloaded cookie state response back to client, with info, for example, the webpage served or the mobile application payload 740. An example reload (or recreate) cookie state response substantially in the form of a HTTP(S) PUSH message 740 (or 745) including XML-formatted data, is provided below:

-   -   PUSH/reloadrecreatecookiestateresposne.php HTTP/1.1     -   Host: www.P-STATE.com     -   Content-Type: Application/XML     -   Content-Length: 667     -   <?XML version=“1.0” encoding=“UTF-8”?>     -   <reload_recreate_cookie_state_response>         -   <state_on_server_status>reloaded</state_on_server_status>     -   //Alternatively, the state_on_server_status may also be         recreated         -   <cookie_session_ID>123adg             -   <state_session_ID>3                 -   <timestamp>2010-05-05-09:40</timestamp>                 -   <merchant_id>A12345</merchant_id>                 -   <merchant>Amazon</merchant>                 -   <merchant_session_id>vme0345</merchant_session_id>         -   <merchant_connection_server>159.2.8.45</merchant_connection_server>             -   <shopping_cart></shopping_cart>             -   <shipper></shipper>             -   <offer></offer>             -   <payment_method> Visa 1234</payment_method>             -   <checkout>1. baby boots 2. books Total $320 Address: 123                 peace st. New York N.Y.</checkout>             -   <search></search>             -   <search_results></search_results>             -   <purchase></purchase>             -   <platform></platform>             -   </state_session_ID>         -   </cookie_session_ID>     -   </reload_recreate_cookie_state_response>

The client may launch target for executing response payload, for example, open browser or application, and load payload in target 750 for display to the user 760. In an alternative embodiment, if the merchant server do not have the selected cookie loaded 725, the merchant server may recreate selected cookie state with payload cookie states (e.g., load cart, search, shipping, pay, etc.) 735 and send it back to the client 745. In another alternative embodiment, the merchant or the client may request the selected cookie from the P-STATE server.

FIG. 8 shows a logic flow diagram illustrating example cookie states reload/recreate component in some embodiments of the P-STATE. In some embodiments, the client may receive a cookie state selection input from the consumer 801. The client may then determine what platform was used to send the input (e.g., webpage, mobile device application, etc.). The client may then generate and send a reload/recreate cookie states request 805 to the merchant server 810. The merchant server may determine if selected cookie state is till loaded on the merchant server 815. If the cookie state is still loaded 822, the merchant server may load selected cookie state and sends reload cookie state response to the client 825. The response may also include a webpage server or application payload 830. Upon receiving the reload cookie state response, the client may launch a target for executing response payload (e.g., open a browser, a mobile device application) and load payload in target for display to the user 835. In some embodiments, if the cookie is no longer loaded at the merchant server 820, in an alternative embodiment, the merchant server may determine if the session can be recreated 840. If the session can be recreated, the merchant server may recreate selected cookie state with actions such as loading card, searching, adding shipping, etc. 855. The merchant server may then send recreate confirmation response message with webpage served or application payload to the client 860. The client may then laugh target and load payload in target 835. Alternatively, if the session can not be recreated 840 at the merchant server, the merchant may send a load cookie state request to the P-STATE server 845 and retrieve cookie states from the P-STATE server. Once the merchant receives cookie states from the P-STATE server 855, the merchant may recreate selected cookie state and send to client to load in target 835

P-STATE Controller

FIG. 9 shows a block diagram illustrating embodiments of a P-STATE controller. In this embodiment, the P-STATE controller 901 may serve to aggregate, process, store, search, serve, identify, instruct, generate, match, and/or facilitate interactions with a computer through various bi-directional linking technologies, and/or other related data.

Typically, users, which may be people and/or other systems, may engage information technology systems (e.g., computers) to facilitate information processing. In turn, computers employ processors to process information; such processors 903 may be referred to as central processing units (CPU). One form of processor is referred to as a microprocessor. CPUs use communicative circuits to pass binary encoded signals acting as instructions to enable various operations. These instructions may be operational and/or data instructions containing and/or referencing other instructions and data in various processor accessible and operable areas of memory 929 (e.g., registers, cache memory, random access memory, etc.). Such communicative instructions may be stored and/or transmitted in batches (e.g., batches of instructions) as programs and/or data components to facilitate desired operations. These stored instruction codes, e.g., programs, may engage the CPU circuit components and other motherboard and/or system components to perform desired operations. One type of program is a computer operating system, which, may be executed by CPU on a computer; the operating system enables and facilitates users to access and operate computer information technology and resources. Some resources that may be employed in information technology systems include: input and output mechanisms through which data may pass into and out of a computer; memory storage into which data may be saved; and processors by which information may be processed. These information technology systems may be used to collect data for later retrieval, analysis, and manipulation, which may be facilitated through a database program. These information technology systems provide interfaces that allow users to access and operate various system components.

In one embodiment, the P-STATE controller 901 may be connected to and/or communicate with entities such as, but not limited to: one or more users from user input devices 911; peripheral devices 912; an optional cryptographic processor device 928; and/or a communications network 913.

Networks are commonly thought to comprise the interconnection and interoperation of clients, servers, and intermediary nodes in a graph topology. It should be noted that the term “server” as used throughout this application refers generally to a computer, other device, program, or combination thereof that processes and responds to the requests of remote users across a communications network. Servers serve their information to requesting “clients.” The term “client” as used herein refers generally to a computer, program, other device, user and/or combination thereof that is capable of processing and making requests and obtaining and processing any responses from servers across a communications network. A computer, other device, program, or combination thereof that facilitates, processes information and requests, and/or furthers the passage of information from a source user to a destination user is commonly referred to as a “node.” Networks are generally thought to facilitate the transfer of information from source points to destinations. A node specifically tasked with furthering the passage of information from a source to a destination is commonly called a “router.” There are many forms of networks such as Local Area Networks (LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks (WLANs), etc. For example, the Internet is generally accepted as being an interconnection of a multitude of networks whereby remote clients and servers may access and interoperate with one another.

The P-STATE controller 901 may be based on computer systems that may comprise, but are not limited to, components such as: a computer systemization 902 connected to memory 929.

Computer Systemization

A computer systemization 902 may comprise a clock 930, central processing unit (“CPU(s)” and/or “processor(s)” (these terms are used interchangeable throughout the disclosure unless noted to the contrary)) 903, a memory 929 (e.g., a read only memory (ROM) 906, a random access memory (RAM) 905, etc.), and/or an interface bus 907, and most frequently, although not necessarily, are all interconnected and/or communicating through a system bus 904 on one or more (mother)board(s) 902 having conductive and/or otherwise transportive circuit pathways through which instructions (e.g., binary encoded signals) may travel to effectuate communications, operations, storage, etc. The computer systemization may be connected to a power source 986; e.g., optionally the power source may be internal. Optionally, a cryptographic processor 926 and/or transceivers (e.g., ICs) 974 may be connected to the system bus. In another embodiment, the cryptographic processor and/or transceivers may be connected as either internal and/or external peripheral devices 912 via the interface bus I/O. In turn, the transceivers may be connected to antenna(s) 975, thereby effectuating wireless transmission and reception of various communication and/or sensor protocols; for example the antenna(s) may connect to: a Texas Instruments WiLink WL1283 transceiver chip (e.g., providing 802.11n, Bluetooth 3.0, FM, global positioning system (GPS) (thereby allowing P-STATE controller to determine its location)); Broadcom BCM4329FKUBG transceiver chip (e.g., providing 802.11n, Bluetooth 2.1+EDR, FM, etc.); a Broadcom BCM4750IUB8 receiver chip (e.g., GPS); an Infineon Technologies X-Gold 618-PMB9800 (e.g., providing 2G/3G HSDPA/HSUPA communications); and/or the like. The system clock typically has a crystal oscillator and generates a base signal through the computer systemization's circuit pathways. The clock is typically coupled to the system bus and various clock multipliers that will increase or decrease the base operating frequency for other components interconnected in the computer systemization. The clock and various components in a computer systemization drive signals embodying information throughout the system. Such transmission and reception of instructions embodying information throughout a computer systemization may be commonly referred to as communications. These communicative instructions may further be transmitted, received, and the cause of return and/or reply communications beyond the instant computer systemization to: communications networks, input devices, other computer systemizations, peripheral devices, and/or the like. It should be understood that in alternative embodiments, any of the above components may be connected directly to one another, connected to the CPU, and/or organized in numerous variations employed as exemplified by various computer systems.

The CPU comprises at least one high-speed data processor adequate to execute program components for executing user and/or system-generated requests. Often, the processors themselves will incorporate various specialized processing units, such as, but not limited to: integrated system (bus) controllers, memory management control units, floating point units, and even specialized processing sub-units like graphics processing units, digital signal processing units, and/or the like. Additionally, processors may include internal fast access addressable memory, and be capable of mapping and addressing memory 929 beyond the processor itself; internal memory may include, but is not limited to: fast registers, various levels of cache memory (e.g., level 1, 2, 3, etc.), RAM, etc. The processor may access this memory through the use of a memory address space that is accessible via instruction address, which the processor can construct and decode allowing it to access a circuit path to a specific memory address space having a memory state. The CPU may be a microprocessor such as: AMD's Athlon, Duron and/or Opteron; ARM's application, embedded and secure processors; IBM and/or Motorola's DragonBall and PowerPC; IBM's and Sony's Cell processor; Intel's Celeron, Core (2) Duo, Itanium, Pentium, Xeon, and/or XScale; and/or the like processor(s). The CPU interacts with memory through instruction passing through conductive and/or transportive conduits (e.g., (printed) electronic and/or optic circuits) to execute stored instructions (i.e., program code) according to conventional data processing techniques. Such instruction passing facilitates communication within the P-STATE controller and beyond through various interfaces. Should processing requirements dictate a greater amount speed and/or capacity, distributed processors (e.g., Distributed P-STATE), mainframe, multi-core, parallel, and/or super-computer architectures may similarly be employed. Alternatively, should deployment requirements dictate greater portability, smaller Personal Digital Assistants (PDAs) may be employed.

Depending on the particular implementation, features of the P-STATE may be achieved by implementing a microcontroller such as CAST's R8051XC2 microcontroller; Intel's MCS 51 (i.e., 8051 microcontroller); and/or the like. Also, to implement certain features of the P-STATE, some feature implementations may rely on embedded components, such as: Application-Specific Integrated Circuit (“ASIC”), Digital Signal Processing (“DSP”), Field Programmable Gate Array (“FPGA”), and/or the like embedded technology. For example, any of the P-STATE component collection (distributed or otherwise) and/or features may be implemented via the microprocessor and/or via embedded components; e.g., via ASIC, coprocessor, DSP, FPGA, and/or the like. Alternately, some implementations of the P-STATE may be implemented with embedded components that are configured and used to achieve a variety of features or signal processing.

Depending on the particular implementation, the embedded components may include software solutions, hardware solutions, and/or some combination of both hardware/software solutions. For example, P-STATE features discussed herein may be achieved through implementing FPGAs, which are a semiconductor devices containing programmable logic components called “logic blocks”, and programmable interconnects, such as the high performance FPGA Virtex series and/or the low cost Spartan series manufactured by Xilinx. Logic blocks and interconnects can be programmed by the customer or designer, after the FPGA is manufactured, to implement any of the P-STATE features. A hierarchy of programmable interconnects allow logic blocks to be interconnected as needed by the P-STATE system designer/administrator, somewhat like a one-chip programmable breadboard. An FPGA's logic blocks can be programmed to perform the operation of basic logic gates such as AND, and XOR, or more complex combinational operators such as decoders or mathematical operations. In most FPGAs, the logic blocks also include memory elements, which may be circuit flip-flops or more complete blocks of memory. In some circumstances, the P-STATE may be developed on regular FPGAs and then migrated into a fixed version that more resembles ASIC implementations. Alternate or coordinating implementations may migrate P-STATE controller features to a final ASIC instead of or in addition to FPGAs. Depending on the implementation all of the aforementioned embedded components and microprocessors may be considered the “CPU” and/or “processor” for the P-STATE.

Power Source

The power source 986 may be of any standard form for powering small electronic circuit board devices such as the following power cells: alkaline, lithium hydride, lithium ion, lithium polymer, nickel cadmium, solar cells, and/or the like. Other types of AC or DC power sources may be used as well. In the case of solar cells, in one embodiment, the case provides an aperture through which the solar cell may capture photonic energy. The power cell 986 is connected to at least one of the interconnected subsequent components of the P-STATE thereby providing an electric current to all subsequent components. In one example, the power source 986 is connected to the system bus component 904. In an alternative embodiment, an outside power source 986 is provided through a connection across the I/O 908 interface. For example, a USB and/or IEEE 1394 connection carries both data and power across the connection and is therefore a suitable source of power.

Interface Adapters

Interface bus(ses) 907 may accept, connect, and/or communicate to a number of interface adapters, conventionally although not necessarily in the form of adapter cards, such as but not limited to: input output interfaces (I/O) 908, storage interfaces 909, network interfaces 910, and/or the like. Optionally, cryptographic processor interfaces 927 similarly may be connected to the interface bus. The interface bus provides for the communications of interface adapters with one another as well as with other components of the computer systemization. Interface adapters are adapted for a compatible interface bus. Interface adapters conventionally connect to the interface bus via a slot architecture. Conventional slot architectures may be employed, such as, but not limited to: Accelerated Graphics Port (AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), and/or the like.

Storage interfaces 909 may accept, communicate, and/or connect to a number of storage devices such as, but not limited to: storage devices 914, removable disc devices, and/or the like. Storage interfaces may employ connection protocols such as, but not limited to: (Ultra) (Serial) Advanced Technology Attachment (Packet Interface) ((Ultra) (Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE), Institute of Electrical and Electronics Engineers (IEEE) 1394, fiber channel, Small Computer Systems Interface (SCSI), Universal Serial Bus (USB), and/or the like.

Network interfaces 910 may accept, communicate, and/or connect to a communications network 913. Through a communications network 913, the P-STATE controller is accessible through remote clients 933 b (e.g., computers with web browsers) by users 933 a. Network interfaces may employ connection protocols such as, but not limited to: direct connect, Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/or the like), Token Ring, wireless connection such as IEEE 802.11a-x, and/or the like. Should processing requirements dictate a greater amount speed and/or capacity, distributed network controllers (e.g., Distributed P-STATE), architectures may similarly be employed to pool, load balance, and/or otherwise increase the communicative bandwidth required by the P-STATE controller. A communications network may be any one and/or the combination of the following: a direct interconnection; the Internet; a Local Area Network (LAN); a Metropolitan Area Network (MAN); an Operating Missions as Nodes on the Internet (OMNI); a secured custom connection; a Wide Area Network (WAN); a wireless network (e.g., employing protocols such as, but not limited to a Wireless Application Protocol (WAP), I-mode, and/or the like); and/or the like. A network interface may be regarded as a specialized form of an input output interface. Further, multiple network interfaces 910 may be used to engage with various communications network types 913. For example, multiple network interfaces may be employed to allow for the communication over broadcast, multicast, and/or unicast networks.

Input Output interfaces (I/O) 908 may accept, communicate, and/or connect to user input devices 911, peripheral devices 912, cryptographic processor devices 928, and/or the like. I/O may employ connection protocols such as, but not limited to: audio: analog, digital, monaural, RCA, stereo, and/or the like; data: Apple Desktop Bus (ADB), IEEE 1394a-b, serial, universal serial bus (USB); infrared; joystick; keyboard; midi; optical; PC AT; PS/2; parallel; radio; video interface: Apple Desktop Connector (ADC), BNC, coaxial, component, composite, digital, Digital Visual Interface (DVI), high-definition multimedia interface (HDMI), RCA, RF antennae, S-Video, VGA, and/or the like; wireless transceivers: 802.11a/b/g/n/x; Bluetooth; cellular (e.g., code division multiple access (CDMA), high speed packet access (HSPA(+)), high-speed downlink packet access (HSDPA), global system for mobile communications (GSM), long term evolution (LTE), WiMax, etc.); and/or the like. One typical output device may include a video display, which typically comprises a Cathode Ray Tube (CRT) or Liquid Crystal Display (LCD) based monitor with an interface (e.g., DVI circuitry and cable) that accepts signals from a video interface, may be used. The video interface composites information generated by a computer systemization and generates video signals based on the composited information in a video memory frame. Another output device is a television set, which accepts signals from a video interface. Typically, the video interface provides the composited video information through a video connection interface that accepts a video display interface (e.g., an RCA composite video connector accepting an RCA composite video cable; a DVI connector accepting a DVI display cable, etc.).

User input devices 911 often are a type of peripheral device 512 (see below) and may include: card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, microphones, mouse (mice), remote controls, retina readers, touch screens (e.g., capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g., accelerometers, ambient light, GPS, gyroscopes, proximity, etc.), styluses, and/or the like.

Peripheral devices 912 may be connected and/or communicate to I/O and/or other facilities of the like such as network interfaces, storage interfaces, directly to the interface bus, system bus, the CPU, and/or the like. Peripheral devices may be external, internal and/or part of the P-STATE controller. Peripheral devices may include: antenna, audio devices (e.g., line-in, line-out, microphone input, speakers, etc.), cameras (e.g., still, video, webcam, etc.), dongles (e.g., for copy protection, ensuring secure transactions with a digital signature, and/or the like), external processors (for added capabilities; e.g., crypto devices 528), force-feedback devices (e.g., vibrating motors), network interfaces, printers, scanners, storage devices, transceivers (e.g., cellular, GPS, etc.), video devices (e.g., goggles, monitors, etc.), video sources, visors, and/or the like. Peripheral devices often include types of input devices (e.g., cameras).

It should be noted that although user input devices and peripheral devices may be employed, the P-STATE controller may be embodied as an embedded, dedicated, and/or monitor-less (i.e., headless) device, wherein access would be provided over a network interface connection.

Cryptographic units such as, but not limited to, microcontrollers, processors 926, interfaces 927, and/or devices 928 may be attached, and/or communicate with the P-STATE controller. A MC68HC16 microcontroller, manufactured by Motorola Inc., may be used for and/or within cryptographic units. The MC68HC16 microcontroller utilizes a 16-bit multiply-and-accumulate instruction in the 16 MHz configuration and requires less than one second to perform a 512-bit RSA private key operation. Cryptographic units support the authentication of communications from interacting agents, as well as allowing for anonymous transactions. Cryptographic units may also be configured as part of the CPU. Equivalent microcontrollers and/or processors may also be used. Other commercially available specialized cryptographic processors include: Broadcom's CryptoNetX and other Security Processors; nCipher's nShield; SafeNet's Luna PCI (e.g., 7100) series; Semaphore Communications' 40 MHz Roadrunner 184; Sun's Cryptographic Accelerators (e.g., Accelerator 6000 PCIe Board, Accelerator 500 Daughtercard); Via Nano Processor (e.g., L2100, L2200, U2400) line, which is capable of performing 500+ MB/s of cryptographic instructions; VLSI Technology's 33 MHz 6868; and/or the like.

Memory

Generally, any mechanization and/or embodiment allowing a processor to affect the storage and/or retrieval of information is regarded as memory 929. However, memory is a fungible technology and resource, thus, any number of memory embodiments may be employed in lieu of or in concert with one another. It is to be understood that the P-STATE controller and/or a computer systemization may employ various forms of memory 929. For example, a computer systemization may be configured wherein the operation of on-chip CPU memory (e.g., registers), RAM, ROM, and any other storage devices are provided by a paper punch tape or paper punch card mechanism; however, such an embodiment would result in an extremely slow rate of operation. In a typical configuration, memory 929 will include ROM 906, RAM 905, and a storage device 914. A storage device 914 may be any conventional computer system storage. Storage devices may include a drum; a (fixed and/or removable) magnetic disk drive; a magneto-optical drive; an optical drive (i.e., Blueray, CD ROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); an array of devices (e.g., Redundant Array of Independent Disks (RAID)); solid state memory devices (USB memory, solid state drives (SSD), etc.); other processor-readable storage mediums; and/or other devices of the like. Thus, a computer systemization generally requires and makes use of memory.

Component Collection

The memory 929 may contain a collection of program and/or database components and/or data such as, but not limited to: operating system component(s) 915 (operating system); information server component(s) 916 (information server); user interface component(s) 917 (user interface); Web browser component(s) 918 (Web browser); database(s) 919; mail server component(s) 921; mail client component(s) 922; cryptographic server component(s) 920 (cryptographic server); the P-STATE component(s) 935; cookie/states storage (“CSS”) component 941; cookie states search presentation (“CSSP”) component 942; and cookie/states reload/recreate (“CSRR”) component 943; and/or the like (i.e., collectively a component collection). These components may be stored and accessed from the storage devices and/or from storage devices accessible through an interface bus. Although non-conventional program components such as those in the component collection, typically, are stored in a local storage device 914, they may also be loaded and/or stored in memory such as: peripheral devices, RAM, remote storage facilities through a communications network, ROM, various forms of memory, and/or the like.

Operating System

The operating system component 915 is an executable program component facilitating the operation of the P-STATE controller. Typically, the operating system facilitates access of I/O, network interfaces, peripheral devices, storage devices, and/or the like. The operating system may be a highly fault tolerant, scalable, and secure system such as: Apple Macintosh OS X (Server); AT&T Plan 9; Be OS; Unix and Unix-like system distributions (such as AT&T's UNIX; Berkley Software Distribution (BSD) variations such as FreeBSD, NetBSD, OpenBSD, and/or the like; Linux distributions such as Red Hat, Ubuntu, and/or the like); and/or the like operating systems. However, more limited and/or less secure operating systems also may be employed such as Apple Macintosh OS, IBM OS/2, Microsoft DOS, Microsoft Windows 2000/2003/3.1/95/98/CE/Millenium/NT/Vista/XP (Server), Palm OS, and/or the like. An operating system may communicate to and/or with other components in a component collection, including itself, and/or the like. Most frequently, the operating system communicates with other program components, user interfaces, and/or the like. For example, the operating system may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. The operating system, once executed by the CPU, may enable the interaction with communications networks, data, I/O, peripheral devices, program components, memory, user input devices, and/or the like. The operating system may provide communications protocols that allow the P-STATE controller to communicate with other entities through a communications network 913. Various communication protocols may be used by the P-STATE controller as a subcarrier transport mechanism for interaction, such as, but not limited to: multicast, TCP/IP, UDP, unicast, and/or the like.

Information Server

An information server component 916 is a stored program component that is executed by a CPU. The information server may be a conventional Internet information server such as, but not limited to Apache Software Foundation's Apache, Microsoft's Internet Information Server, and/or the like. The information server may allow for the execution of program components through facilities such as Active Server Page (ASP), ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, Common Gateway Interface (CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH, Java, JavaScript, Practical Extraction Report Language (PERL), Hypertext Pre-Processor (PHP), pipes, Python, wireless application protocol (WAP), WebObjects, and/or the like. The information server may support secure communications protocols such as, but not limited to, File Transfer Protocol (FTP); HyperText Transfer Protocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS), Secure Socket Layer (SSL), messaging protocols (e.g., America Online (AOL) Instant Messenger (AIM), Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), Microsoft Network (MSN) Messenger Service, Presence and Instant Messaging Protocol (PRIM), Internet Engineering Task Force's (IETF's) Session Initiation Protocol (SIP), SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE), open XML-based Extensible Messaging and Presence Protocol (XMPP) (i.e., Jabber or Open Mobile Alliance's (OMA's) Instant Messaging and Presence Service (IMPS)), Yahoo! Instant Messenger Service, and/or the like. The information server provides results in the form of Web pages to Web browsers, and allows for the manipulated generation of the Web pages through interaction with other program components. After a Domain Name System (DNS) resolution portion of an HTTP request is resolved to a particular information server, the information server resolves requests for information at specified locations on the P-STATE controller based on the remainder of the HTTP request. For example, a request such as http://123.124.125.126/myInformation.html might have the IP portion of the request “123.124.125.126” resolved by a DNS server to an information server at that IP address; that information server might in turn further parse the http request for the “/myInformation.html” portion of the request and resolve it to a location in memory containing the information “myInformation.html.” Additionally, other information serving protocols may be employed across various ports, e.g., FTP communications across port 21, and/or the like. An information server may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the information server communicates with the P-STATE database 919, operating systems, other program components, user interfaces, Web browsers, and/or the like.

Access to the P-STATE database may be achieved through a number of database bridge mechanisms such as through scripting languages as enumerated below (e.g., CGI) and through inter-application communication channels as enumerated below (e.g., CORBA, WebObjects, etc.). Any data requests through a Web browser are parsed through the bridge mechanism into appropriate grammars as required by the P-STATE. In one embodiment, the information server would provide a Web form accessible by a Web browser. Entries made into supplied fields in the Web form are tagged as having been entered into the particular fields, and parsed as such. The entered terms are then passed along with the field tags, which act to instruct the parser to generate queries directed to appropriate tables and/or fields. In one embodiment, the parser may generate queries in standard SQL by instantiating a search string with the proper join/select commands based on the tagged text entries, wherein the resulting command is provided over the bridge mechanism to the P-STATE as a query. Upon generating query results from the query, the results are passed over the bridge mechanism, and may be parsed for formatting and generation of a new results Web page by the bridge mechanism. Such a new results Web page is then provided to the information server, which may supply it to the requesting Web browser.

Also, an information server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.

User Interface

Computer interfaces in some respects are similar to automobile operation interfaces. Automobile operation interface elements such as steering wheels, gearshifts, and speedometers facilitate the access, operation, and display of automobile resources, and status. Computer interaction interface elements such as check boxes, cursors, menus, scrollers, and windows (collectively and commonly referred to as widgets) similarly facilitate the access, capabilities, operation, and display of data and computer hardware and operating system resources, and status. Operation interfaces are commonly called user interfaces. Graphical user interfaces (GUIs) such as the Apple Macintosh Operating System's Aqua, IBM's OS/2, Microsoft's Windows 2000/2003/3.1/95/98/CE/Millenium/NT/XP/Vista/7 (i.e., Aero), Unix's X-Windows (e.g., which may include additional Unix graphic interface libraries and layers such as K Desktop Environment (KDE), mythTV and GNU Network Object Model Environment (GNOME)), web interface libraries (e.g., ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, etc. interface libraries such as, but not limited to, Dojo, jQuery(UI), MooTools, Prototype, script.aculo.us, SWFObject, Yahoo! User Interface, any of which may be used and) provide a baseline and means of accessing and displaying information graphically to users.

A user interface component 917 is a stored program component that is executed by a CPU. The user interface may be a conventional graphic user interface as provided by, with, and/or atop operating systems and/or operating environments such as already discussed. The user interface may allow for the display, execution, interaction, manipulation, and/or operation of program components and/or system facilities through textual and/or graphical facilities. The user interface provides a facility through which users may affect, interact, and/or operate a computer system. A user interface may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the user interface communicates with operating systems, other program components, and/or the like. The user interface may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.

Web Browser

A Web browser component 918 is a stored program component that is executed by a CPU. The Web browser may be a conventional hypertext viewing application such as Microsoft Internet Explorer or Netscape Navigator. Secure Web browsing may be supplied with 128 bit (or greater) encryption by way of HTTPS, SSL, and/or the like. Web browsers allowing for the execution of program components through facilities such as ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-in APIs (e.g., FireFox, Safari Plug-in, and/or the like APIs), and/or the like. Web browsers and like information access tools may be integrated into PDAs, cellular telephones, and/or other mobile devices. A Web browser may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the Web browser communicates with information servers, operating systems, integrated program components (e.g., plug-ins), and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. Also, in place of a Web browser and information server, a combined application may be developed to perform similar operations of both. The combined application would similarly affect the obtaining and the provision of information to users, user agents, and/or the like from the P-STATE enabled nodes. The combined application may be nugatory on systems employing standard Web browsers.

Mail Server

A mail server component 921 is a stored program component that is executed by a CPU 903. The mail server may be a conventional Internet mail server such as, but not limited to sendmail, Microsoft Exchange, and/or the like. The mail server may allow for the execution of program components through facilities such as ASP, ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, CGI scripts, Java, JavaScript, PERL, PHP, pipes, Python, WebObjects, and/or the like. The mail server may support communications protocols such as, but not limited to: Internet message access protocol (IMAP), Messaging Application Programming Interface (MAPI)/Microsoft Exchange, post office protocol (POP3), simple mail transfer protocol (SMTP), and/or the like. The mail server can route, forward, and process incoming and outgoing mail messages that have been sent, relayed and/or otherwise traversing through and/or to the P-STATE.

Access to the P-STATE mail may be achieved through a number of APIs offered by the individual Web server components and/or the operating system.

Also, a mail server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses.

Mail Client

A mail client component 922 is a stored program component that is executed by a CPU 903. The mail client may be a conventional mail viewing application such as Apple Mail, Microsoft Entourage, Microsoft Outlook, Microsoft Outlook Express, Mozilla, Thunderbird, and/or the like. Mail clients may support a number of transfer protocols, such as: IMAP, Microsoft Exchange, POP3, SMTP, and/or the like. A mail client may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the mail client communicates with mail servers, operating systems, other mail clients, and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses. Generally, the mail client provides a facility to compose and transmit electronic mail messages.

Cryptographic Server

A cryptographic server component 920 is a stored program component that is executed by a CPU 903, cryptographic processor 926, cryptographic processor interface 927, cryptographic processor device 928, and/or the like. Cryptographic processor interfaces will allow for expedition of encryption and/or decryption requests by the cryptographic component; however, the cryptographic component, alternatively, may run on a conventional CPU. The cryptographic component allows for the encryption and/or decryption of provided data. The cryptographic component allows for both symmetric and asymmetric (e.g., Pretty Good Protection (PGP)) encryption and/or decryption. The cryptographic component may employ cryptographic techniques such as, but not limited to: digital certificates (e.g., X.509 authentication framework), digital signatures, dual signatures, enveloping, password access protection, public key management, and/or the like. The cryptographic component will facilitate numerous (encryption and/or decryption) security protocols such as, but not limited to: checksum, Data Encryption Standard (DES), Elliptical Curve Encryption (ECC), International Data Encryption Algorithm (IDEA), Message Digest 5 (MD5, which is a one way hash operation), passwords, Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption and authentication system that uses an algorithm developed in 1977 by Ron Rivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA), Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS), and/or the like. Employing such encryption security protocols, the P-STATE may encrypt all incoming and/or outgoing communications and may serve as node within a virtual private network (VPN) with a wider communications network. The cryptographic component facilitates the process of “security authorization” whereby access to a resource is inhibited by a security protocol wherein the cryptographic component effects authorized access to the secured resource. In addition, the cryptographic component may provide unique identifiers of content, e.g., employing and MD5 hash to obtain a unique signature for an digital audio file. A cryptographic component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. The cryptographic component supports encryption schemes allowing for the secure transmission of information across a communications network to enable the P-STATE component to engage in secure transactions if so desired. The cryptographic component facilitates the secure accessing of resources on the P-STATE and facilitates the access of secured resources on remote systems; i.e., it may act as a client and/or server of secured resources. Most frequently, the cryptographic component communicates with information servers, operating systems, other program components, and/or the like. The cryptographic component may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.

The P-STATE Database

The P-STATE database component 919 may be embodied in a database and its stored data. The database is a stored program component, which is executed by the CPU; the stored program component portion configuring the CPU to process the stored data. The database may be a conventional, fault tolerant, relational, scalable, secure database such as Oracle or Sybase. Relational databases are an extension of a flat file. Relational databases consist of a series of related tables. The tables are interconnected via a key field. Use of the key field allows the combination of the tables by indexing against the key field; i.e., the key fields act as dimensional pivot points for combining information from various tables. Relationships generally identify links maintained between tables by matching primary keys. Primary keys represent fields that uniquely identify the rows of a table in a relational database. More precisely, they uniquely identify rows of a table on the “one” side of a one-to-many relationship.

Alternatively, the P-STATE database may be implemented using various standard data-structures, such as an array, hash, (linked) list, struct, structured text file (e.g., XML), table, and/or the like. Such data-structures may be stored in memory and/or in (structured) files. In another alternative, an object-oriented database may be used, such as Frontier, ObjectStore, Poet, Zope, and/or the like. Object databases can include a number of object collections that are grouped and/or linked together by common attributes; they may be related to other object collections by some common attributes. Object-oriented databases perform similarly to relational databases with the exception that objects are not just pieces of data but may have other types of capabilities encapsulated within a given object. If the P-STATE database is implemented as a data-structure, the use of the P-STATE database 919 may be integrated into another component such as the P-STATE component 935. Also, the database may be implemented as a mix of data structures, objects, and relational structures. Databases may be consolidated and/or distributed in countless variations through standard data processing techniques. Portions of databases, e.g., tables, may be exported and/or imported and thus decentralized and/or integrated.

In one embodiment, the database component 919 includes several tables 919 a-0. A user table 919 a includes fields such as, but not limited to: a user_ID, name, home_address, work_address, telephone_number, email, merchant_ID client_id, account_id, and/or the like. The user table may support and/or track multiple entity accounts on a P-STATE. A merchant/service provider table 919 b includes fields such as, but not limited to: merchant_ID, merchant_name, merchant_location, merchant_address, merchant_category_code, merchant_api_key, loyalty_program_ID and/or the like. A customer profile table 919 c includes fields such as, but not limited to: user_ID, merchant_ID, payment_card_ID, preferred_payment_type, demographics, prefetch_preferences, and/or the like. A permissions table 919 d includes fields such as, but not limited to: customer ID, transaction execution authorization status, confirmation authorization status, billing authorization status, subscription payment authorization status, and/or the like. A payment card table 919 e includes fields such as, but not limited to: payment_card_id, user_id, identifier, brand, expiration date, spending limit, billing address, issuer, name, nick name, loyalty program ID, and/or the like. A billing agreement table 919 f includes fields such as, but not limited to: customer_id, billing_id, billing_date, billing_amount_limit, confirmation_requirement, authentication_level, billing_authorization_status, and/or the like. A redemption table 919 g includes fields such as, but not limited to: customer_id, loyalty_program_id, coupon_id, redemption_date, redemption_time, redemption_amount, redemption_type, transaction_id, and/or the like. A loyalty table 919 h includes fields such as, but not limited to: loyalty program ID, rules, loyalty currency amount, loyalty expiry date, transaction ID, and/or the like. A coupons table 919 i includes fields such as, but not limited to: coupon ID, coupon value, coupon accepted location, coupon expiry date, and/or the like. A wish list table 919 j includes fields such as, but not limited to: wish list ID, merchant ID, item ID, and/or the like. A shopping lists table 919 k includes fields such as, but not limited to: shopping_lists_ID, merchant_ID, item_ID, transaction_ID, and/or the like. A store injections table 919 l includes fields such as, but not limited to: store_injection_id, merchant_id, item_id, and/or the like. A transaction table 919 m includes fields such as, but not limited to: transaction_id, merchant_id, user_id, session_id, date, time, item_model, manufacturer, price, item_id, and/or the like. A products table 919 n includes fields such as, but not limited to: product_id, merchant_id, item_id, and/or the like. A cookie_states table 9190 includes fields such as, but not limited to: cookie_states_id, cookie_session_id, states_session_id, merchant_id, timestamp, shopping_list_id, payment_method_id, payment_card_id, search, search_results, platform, checkout, shipper, offer, and/or the like.

An Account table 919 e includes fields such as, but not limited to: account_id, account_PAN, account_type, brand, expiration date, spending limit, billing address, issuer, name, nick name, loyalty program ID, and/or the like. A third parties table 919 f includes fields such as, but not limited to: 3^(rd)_parties_ID, 3^(rd)_parties_name, 3^(rd)_parties_type, 3^(rd)_parties_location, 3^(rd)_parties_address, 3^(rd)_parties_api_key, prefetch_request_id, user_id, merchant_id, security_credentials, and/or the like. A redemption table 919 g includes fields such as, but not limited to: customer ID, loyalty program ID, coupon ID, redemption date, redemption time, redemption amount, redemption type, transaction ID, and/or the like. A loyalty table 919 h includes fields such as, but not limited to: loyalty program ID, rules, loyalty currency amount, loyalty expiry date, transaction ID, and/or the like. A coupons table 919 i includes fields such as, but not limited to: coupon ID, coupon value, coupon accepted location, coupon expiry date, and/or the like. A wish list table 919 j includes fields such as, but not limited to: wish list ID, merchant ID, item ID, and/or the like. A plug-ins table 919 k includes fields such as, but not limited to: plug-in ID, plug-in provider ID (merchant ID, issuer ID, etc.), plug-in type, plug-in function, plug-in installation guide, plug-in authorization, plug-in restrictions, and/or the like. A client cookies table 919 l includes fields such as, but not limited to: client_cookie_id, session_ID, client_id, user_id, merchant_id, wallet_id, merchant_login, wallet_login, cookie_timestamp, cookie_address, and/or the like. An account balance table 919 m includes fields such as, but not limited to: user_ID, Account_ID, issuer, api key, balance amount, balance retrieval date/time, and/or the like. and/or the like. A payments table 919 n includes fields such as, but not limited to: user_id, billing ID, billing date, billing amount, Account_ID, authentication level, and/or the like. A prefetch requests table 9190 includes fields such as, but not limited to: prefetch_requests_id, user_id, client_id, 3^(rd)_parties_id, api_id, prefetch_info_type, prefetch_info_value, and/or the like.

In one embodiment, the P-STATE database may interact with other database systems. For example, employing a distributed database system, queries and data access by search P-STATE component may treat the combination of the P-STATE database, an integrated data security layer database as a single database entity.

In one embodiment, user programs may contain various user interface primitives, which may serve to update the P-STATE. Also, various accounts may require custom database tables depending upon the environments and the types of clients the P-STATE may need to serve. It should be noted that any unique fields may be designated as a key field throughout. In an alternative embodiment, these tables have been decentralized into their own databases and their respective database controllers (i.e., individual database controllers for each of the above tables). Employing standard data processing techniques, one may further distribute the databases over several computer systemizations and/or storage devices. Similarly, configurations of the decentralized database controllers may be varied by consolidating and/or distributing the various database components 919 a-0. The P-STATE may be configured to keep track of various settings, inputs, and parameters via database controllers.

The P-STATE database may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the P-STATE database communicates with the P-STATE component, other program components, and/or the like. The database may contain, retain, and provide information regarding other nodes and data.

The P-STATEs

The P-STATE component 935 is a stored program component that is executed by a CPU. In one embodiment, the P-STATE component incorporates any and/or all combinations of the aspects of the P-STATE that was discussed in the previous figures. As such, the P-STATE affects accessing, obtaining and the provision of information, services, transactions, and/or the like across various communications networks.

The P-STATE transforms inputs such as purchase action input (e.g., 211), cookie states search criteria input (e.g., 511), and cookie states selection input (e.g., 711) via P-STATE components such as cookie/states storage (“CSS”) component 941; cookie states search presentation (“CSSP”) component 942; and cookie/states reload/recreate (“CSRR”) component 943, into cookie state presentation (e.g., 525, 760) outputs.

The P-STATE component enabling access of information between nodes may be developed by employing standard development tools and languages such as, but not limited to: Apache components, Assembly, ActiveX, binary executables, (ANSI) (Objective-) C (++), C# and/or .NET, database adapters, CGI scripts, Java, JavaScript, mapping tools, procedural and object oriented development tools, PERL, PHP, Python, shell scripts, SQL commands, web application server extensions, web development environments and libraries (e.g., Microsoft's ActiveX; Adobe AIR, FLEX & FLASH; AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools; Prototype; script.aculo.us; Simple Object Access Protocol (SOAP); SWFObject; Yahoo! User Interface; and/or the like), WebObjects, and/or the like. In one embodiment, the P-STATE server employs a cryptographic server to encrypt and decrypt communications. The P-STATE component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the P-STATE component communicates with the P-STATE database, operating systems, other program components, and/or the like. The P-STATE may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.

Distributed P-STATEs

The structure and/or operation of any of the P-STATE node controller components may be combined, consolidated, and/or distributed in any number of ways to facilitate development and/or deployment. Similarly, the component collection may be combined in any number of ways to facilitate deployment and/or development. To accomplish this, one may integrate the components into a common code base or in a facility that can dynamically load the components on demand in an integrated fashion.

The component collection may be consolidated and/or distributed in countless variations through standard data processing and/or development techniques. Multiple instances of any one of the program components in the program component collection may be instantiated on a single node, and/or across numerous nodes to improve performance through load-balancing and/or data-processing techniques. Furthermore, single instances may also be distributed across multiple controllers and/or storage devices; e.g., databases. All program component instances and controllers working in concert may do so through standard data processing communication techniques.

The configuration of the P-STATE controller will depend on the context of system deployment. Factors such as, but not limited to, the budget, capacity, location, and/or use of the underlying hardware resources may affect deployment requirements and configuration. Regardless of if the configuration results in more consolidated and/or integrated program components, results in a more distributed series of program components, and/or results in some combination between a consolidated and distributed configuration, data may be communicated, obtained, and/or provided. Instances of components consolidated into a common code base from the program component collection may communicate, obtain, and/or provide data. This may be accomplished through intra-application data processing communication techniques such as, but not limited to: data referencing (e.g., pointers), internal messaging, object instance variable communication, shared memory space, variable passing, and/or the like.

If component collection components are discrete, separate, and/or external to one another, then communicating, obtaining, and/or providing data with and/or to other component components may be accomplished through inter-application data processing communication techniques such as, but not limited to: Application Program Interfaces (API) information passage; (distributed) Component Object Model ((D)COM), (Distributed) Object Linking and Embedding ((D)OLE), and/or the like), Common Object Request Broker Architecture (CORBA), Jini local and remote application program interfaces, JavaScript Object Notation (JSON), Remote Method Invocation (RMI), SOAP, process pipes, shared files, and/or the like. Messages sent between discrete component components for inter-application communication or within memory spaces of a singular component for intra-application communication may be facilitated through the creation and parsing of a grammar. A grammar may be developed by using development tools such as lex, yacc, XML, and/or the like, which allow for grammar generation and parsing capabilities, which in turn may form the basis of communication messages within and between components.

For example, a grammar may be arranged to recognize the tokens of an HTTP post command, e.g.:

-   -   w3c -post http:// . . . Value1

where Value1 is discerned as being a parameter because “http://” is part of the grammar syntax, and what follows is considered part of the post value. Similarly, with such a grammar, a variable “Value1” may be inserted into an “http://” post command and then sent. The grammar syntax itself may be presented as structured data that is interpreted and/or otherwise used to generate the parsing mechanism (e.g., a syntax description text file as processed by lex, yacc, etc.). Also, once the parsing mechanism is generated and/or instantiated, it itself may process and/or parse structured data such as, but not limited to: character (e.g., tab) delineated text, HTML, structured text streams, XML, and/or the like structured data. In another embodiment, inter-application data processing protocols themselves may have integrated and/or readily available parsers (e.g., JSON, SOAP, and/or like parsers) that may be employed to parse (e.g., communications) data. Further, the parsing grammar may be used beyond message parsing, but may also be used to parse: databases, data collections, data stores, structured data, and/or the like. Again, the desired configuration will depend upon the context, environment, and requirements of system deployment.

For example, in some implementations, the P-STATE controller may be executing a PHP script implementing a Secure Sockets Layer (“SSL”) socket server via the information sherver, which listens to incoming communications on a server port to which a client may send data, e.g., data encoded in JSON format. Upon identifying an incoming communication, the PHP script may read the incoming message from the client device, parse the received JSON-encoded text data to extract information from the JSON-encoded text data into PHP script variables, and store the data (e.g., client identifying information, etc.) and/or extracted information in a relational database accessible using the Structured Query Language (“SQL”). An exemplary listing, written substantially in the form of PHP/SQL commands, to accept JSON-encoded input data from a client device via a SSL connection, parse the data to extract variables, and store the data to a database, is provided below:

-   -   <?PHP     -   header(‘Content-Type: text/plain’);     -   // set ip address and port to listen to for incoming data     -   $address=‘192.168.0.100’;     -   $port=255;     -   // create a server-side SSL socket, listen for/accept incoming         communication $sock=socket_create(AF_INET, SOCK_STREAM, 0);     -   socket_bind($sock, $address, $port) or die(‘Could not bind to         address’);     -   socket_listen($sock);     -   $client=socket_accept($sock);     -   // read input data from client device in 1024 byte blocks until         end of message do {         -   $input=         -   $input=socket read($client, 1024);         -   $data.=$input;     -   } while ($input !=“ ”);     -   // parse data to extract variables     -   $obj=json_decode($data, true);     -   // store input data in a database     -   mysgl_connect(“201.408.185.132”,$DBserver,$password); // access         database server mysgl_select(“CLIENT_DB.SQL”); // select         database to append     -   mysgl_query(“INSERT INTO UserTable (transmission)     -   VALUES ($data)”); // add data to UserTable table in a CLIENT         database mysglclose(“CLIENTDB.SQL”); // close connection to         database     -   ?>

Also, the following resources may be used to provide example embodiments regarding SOAP parser implementation:

-   -   http://www.xay.com/perl/site/lib/SOAP/Parser.html     -   http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDI.doc/referenceguide295.htm

and other parser implementations:

-   -   http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDI.doc/referenceguide259.htm

all of which are hereby expressly incorporated by reference.

In order to address various issues and advance the art, the entirety of this application for REMOTE DECOUPLED APPLICATION PERSISTENT STATE APPARATUSES, METHODS AND SYSTEMS (including the Cover Page, Title, Headings, Field, Background, Summary, Brief Description of the Drawings, Detailed Description, Claims, Abstract, Figures, Appendices, and otherwise) shows, by way of illustration, various embodiments in which the claimed innovations may be practiced. The advantages and features of the application are of a representative sample of embodiments only, and are not exhaustive and/or exclusive. They are presented only to assist in understanding and teach the claimed principles. It should be understood that they are not representative of all claimed innovations. As such, certain aspects of the disclosure have not been discussed herein. That alternate embodiments may not have been presented for a specific portion of the innovations or that further undescribed alternate embodiments may be available for a portion is not to be considered a disclaimer of those alternate embodiments. It will be appreciated that many of those undescribed embodiments incorporate the same principles of the innovations and others are equivalent. Thus, it is to be understood that other embodiments may be utilized and functional, logical, operational, organizational, structural and/or topological modifications may be made without departing from the scope and/or spirit of the disclosure. As such, all examples and/or embodiments are deemed to be non-limiting throughout this disclosure. Also, no inference should be drawn regarding those embodiments discussed herein relative to those not discussed herein other than it is as such for purposes of reducing space and repetition. For instance, it is to be understood that the logical and/or topological structure of any combination of any program components (a component collection), other components and/or any present feature sets as described in the figures and/or throughout are not limited to a fixed operating order and/or arrangement, but rather, any disclosed order is exemplary and all equivalents, regardless of order, are contemplated by the disclosure. Furthermore, it is to be understood that such features are not limited to serial execution, but rather, any number of threads, processes, services, servers, and/or the like that may execute asynchronously, concurrently, in parallel, simultaneously, synchronously, and/or the like are contemplated by the disclosure. As such, some of these features may be mutually contradictory, in that they cannot be simultaneously present in a single embodiment. Similarly, some features are applicable to one aspect of the innovations, and inapplicable to others. In addition, the disclosure includes other innovations not presently claimed. Applicant reserves all rights in those presently unclaimed innovations including the right to claim such innovations, file additional applications, continuations, continuations in part, divisions, and/or the like thereof. As such, it should be understood that advantages, embodiments, examples, functional, features, logical, operational, organizational, structural, topological, and/or other aspects of the disclosure are not to be considered limitations on the disclosure as defined by the claims or limitations on equivalents to the claims. It is to be understood that, depending on the particular needs and/or characteristics of a P-STATE individual and/or enterprise user, database configuration and/or relational model, data type, data transmission and/or network framework, syntax structure, and/or the like, various embodiments of the P-STATE, may be implemented that enable a great deal of flexibility and customization. For example, aspects of the P-STATE may be adapted for system latency reduction. While various embodiments and discussions of the P-STATE have been directed to prefetching and on-demand fetching user account information, however, it is to be understood that the embodiments described herein may be readily configured and/or customized for a wide variety of other applications and/or implementations. 

What is claimed is:
 1. A method comprising: receiving, at a persistent state server, at least one selection from a first user device associated with a user; creating and storing, at the persistent state server remote from the first user device, a first cookie associated with one or more states of a user account of the user that reflects the at least one selection from the first user device; receiving, at the persistent state server from a second user device remote from the persistent state server, a request for state data related to the one or more states of the user account; identifying, by the persistent state server, the first cookie in response to the request for state data; determining, by the persistent state server, a platform type of the second user device; generating, by the persistent state server, a second cookie compliant with the platform type of the second user device based on the first cookie, the second cookie including instructions to present the at least one selection on the second user device via the platform type of the second user device; and in response to receiving the request for state data, sending the generated second cookie from the persistent state server to the second user device for launching, by the persistent state server, a target for executing the second cookie.
 2. The method of claim 1, wherein the first cookie stores a state of the user's selection history associated with the user account.
 3. The method of claim 2, wherein the first cookie contains multiple states.
 4. The method of claim 3 further comprising providing cloud-based storage to a merchant associated with the at least one selection such that the user can retrieve any of the multiple states associated with the merchant.
 5. The method of claim 1, wherein the first cookie is stored in a database associated with the user account.
 6. The method of claim 5 further comprising providing a user interface for searching the database.
 7. The method of claim 1, wherein the first cookie is used to recognize that the user has previously paid for the at least one selection.
 8. The method of claim 1, wherein the first cookie includes at least one of a timestamp of when at least one selection took place, a merchant associated with the at least one selection, purchase status, or a platform type of the first user device.
 9. The method of claim 1, wherein multiple states of a user's selection history are combined into the first cookie.
 10. The method of claim 9 further comprising providing a preview window to facilitate viewing the multiple states included in the first cookie.
 11. A non-transitory computer readable medium storing instructions that, when executed, cause an apparatus at least to perform: receiving, at a persistent state server, at least one selection from a first user device associated with a user; creating and storing, at the persistent state server remote from the first user device, a first cookie associated with a one or more states of a user account of the user that reflects the at least one selection from the first user device; receiving, at the persistent state server from a second user device remote from the persistent state server, a request for state data related to the one or more states of the user account; identifying, by the persistent state server, the first cookie in response to the request for state data; determining, by the persistent state server, a platform type of the second user device; generating, by the persistent state server, a second cookie compliant with the platform type of the second user device based on the first cookie, the second cookie including instructions to present the at least one selection on the second user device via the platform type of the second user device; and in response to receiving the request for state data, sending the generated second cookie from the persistent state server to the second user device for launching, by the persistent state server, a target for executing the second cookie.
 12. The non-transitory computer readable medium of claim 11, wherein the first cookie stores a state of the user's selection history associated with the user account.
 13. The non-transitory computer readable medium of claim 12, wherein the first cookie contains multiple states.
 14. The non-transitory computer readable medium of claim 13 further comprising providing cloud-based storage to a merchant associated with the at least one selection such that the user can retrieve any of the multiple states associated with the merchant.
 15. The non-transitory computer readable medium of claim 11, wherein the first cookie is stored in a database associated with the user account.
 16. The non-transitory computer readable medium of claim 15, further comprising instructions causing the apparatus to perform providing a user interface for searching the database.
 17. The non-transitory computer readable medium of claim 11, wherein the first cookie is used to recognize that the user has previously paid for the at least one selection.
 18. A platform-specific cookie generating apparatus comprising: a memory; and a processor disposed in communication with said memory, and configured to issue a plurality of processing instructions stored in the memory, wherein the processor issues instructions to: receive, at a persistent state server, at least one selection from a first user device associated with a user; create and store, at the persistent state server remote from the first user device, a first cookie associated with a one or more states of a user account of the user that reflects the at least one selection; receive, at the persistent state server from a second user device remote from the persistent state server, a request for state data related to the one or more states of the user account; identify, by the persistent state server, the first cookie in response to the request for state data; determine, by the persistent state server, a platform type of the second user device; generate, by the persistent state server, a second cookie compliant with the platform type of the second user device based on the first cookie, the second cookie including instructions to present the at least one selection on the second user device via the platform type of the second user device; and in response to receiving the request for state data, sending the generated second cookie from the persistent state server to the second user device for launch, by the persistent state server, a target for executing the second cookie.
 19. The apparatus of claim 18, wherein the first cookie stores a state of the user's selection history associated with the user account.
 20. The apparatus of claim 19, wherein the first cookie contains multiple states. 